Product NPS Survey Template

NPS is a conversation starter, not a score. This product NPS survey template captures why users would — or wouldn't — recommend your product across 4 targeted questions that surface loyalty signals, feature wins, and the one change that matters most.

Try 14 days for Free
Lightening fast setup

A product NPS survey template that goes beyond the single-number score. Four questions — recommendation likelihood, feature strengths, improvement areas, and the one change users want most — in under a minute. That gives you a leading indicator of retention plus the qualitative signal to act on it. Pair it with Zonka Feedback's NPS engine to segment respondents, trigger workflows, and close the loop automatically.

4 Questions

5 Screens

30 secs to complete

What Questions Are in This Product NPS Survey Template?

This product NPS survey template includes 4 questions across 5 screens — one quantitative score and three qualitative follow-ups. The pairing is deliberate: the score tells you where you stand, and the follow-ups tell you why from three different angles. Here's what each question does and why it earns its place:

"How likely are you to recommend our product to a friend or colleague?" (0-10 scale) — This is Reichheld's original Net Promoter Score question applied to your product specifically. The 0-10 scale splits respondents into three groups: Promoters (9-10), Passives (7-8), and Detractors (0-6). Product teams that track this number weekly spot retention problems 2-3 weeks before they show up in churn data. The key is the trend line, not any single score.
"We'd love to learn which features of our product impressed you the most?" (open-ended) — The positive signal question. This tells you what's working — and more importantly, what users value enough to mention unprompted. When 40% of respondents name the same feature, that's your competitive moat. Protect it, double down on it, and make sure it stays great. Teams that only ask "what's broken" miss the equally important question of "what's keeping people here." Run responses through thematic analysis to cluster feature mentions into patterns.
"What do you suggest we can improve in the product for your experience to be great?" (open-ended) — The improvement signal. This question catches the friction points that don't show up in usage analytics — confusing workflows, missing integrations, features that almost work but not quite. The phrasing "for your experience to be great" sets an aspirational frame that pulls more constructive responses than "what's wrong." Pair with AI-powered feedback analytics to auto-tag recurring improvement themes across hundreds of responses.
"What is the one thing you'd like to change about the product to improve your experience?" (open-ended) — The prioritization question. Where the previous question asks broadly, this one forces a single answer. That constraint is the point — it makes respondents choose their top pain point instead of listing five. When you aggregate these single-answer responses, the #1 most-mentioned change is your next product priority. No roadmap debate needed — your users just voted.

Three open-ended questions might seem redundant, but each serves a different purpose: what's great (retain it), what needs improving (fix it broadly), and the single most important change (fix it first). Together they give product teams a complete feedback picture that a score-only NPS survey never delivers.

What's a Good Product NPS Score — and Why Most Teams Misread It

Here's the uncomfortable truth about product NPS benchmarks: they vary wildly by vertical, and comparing your SaaS product's score to Apple's is meaningless. What matters is your own trend line and how you compare to direct competitors in your category.

SaaS products: Average NPS sits between 30-40. Top-quartile products hit 50+. Below 20 means you've got a retention problem that marketing spend won't fix.
Consumer apps: Higher variance — gaming apps can swing from -10 to 70 depending on the update cycle. Utility apps tend to cluster around 25-35.
B2B products: Typically 30-50 for healthy products. Enterprise products with high switching costs sometimes score lower (20-30) because users tolerate friction they can't easily escape — which masks problems until contract renewal.

The mistake most teams make: obsessing over the absolute number instead of watching the delta. A score that drops from 45 to 38 in a quarter tells you more than a stable 50. Track your product NPS survey template results weekly, compare month-over-month, and watch for sustained movement — not blips. Use NPS dashboard reports to visualize the trend without manually pulling data.

Pro tip: Segment your product NPS by user cohort — new users (0-30 days), active users (30-180 days), and power users (180+ days). You'll almost always see different scores across cohorts. If new users score low but power users score high, you have an onboarding problem, not a product problem. If the reverse, you have a depth problem.

Product NPS vs Relationship NPS vs Transactional NPS — When to Use Which

NPS is not one thing. There are three flavors, and most teams run the wrong one at the wrong time. A product NPS survey template serves a specific purpose — here's how it compares:

Product NPS (this template) — Measures loyalty toward your product specifically. Best deployed in-app or via email surveys after meaningful product usage. The question explicitly references the product, not your company. Use this when you want to understand product-market fit and feature satisfaction.
Relationship NPS — Measures overall brand/company loyalty. Sent periodically (quarterly, semi-annually) regardless of any specific interaction. Broader scope — captures how customers feel about your company as a whole, including support, pricing, and trust. Read more on relationship vs transactional NPS.
Transactional NPS — Measures loyalty after a specific interaction (support ticket resolved, purchase completed, feature released). Highly contextual and time-sensitive. Use this when you want to evaluate a touchpoint, not the full product.

The error: running relationship NPS and thinking it tells you about your product. It doesn't. A customer can love your support team and tolerate a mediocre product — or love the product and hate your billing process. Product NPS isolates the product signal from the noise.

How to Customize This Product NPS Survey Template

4 questions sounds minimal, and that's the point — response rates on NPS surveys drop sharply after question three. But you can customize how those 4 questions work without adding bloat:

Customize the follow-up by segment. Use conditional logic to show different follow-up questions based on the score. Detractors (0-6) see: "What frustrated you most?" Passives (7-8) see: "What's one thing that would make you a 9 or 10?" Promoters (9-10) see: "What do you love most about the product?" Same survey, three different conversations.
Add a CES or CSAT question — but only one. If you need more signal, bolt on a single Customer Effort Score question ("How easy was it to accomplish your goal?") or a CSAT rating. Three questions is the ceiling for in-product surveys. Four and you'll feel the completion rate drop.
Personalize with contact properties. Pipe in the user's name and the specific feature they last used via pre-filled survey data. "Based on your experience with [Feature Name], how likely are you to recommend..." converts better than generic wording because it signals you're paying attention.
Brand it. White-label the survey with your logo, colors, and domain. Build it in Zonka's survey builder — an unbranded survey looks like spam inside a polished product.

Closing the Loop on Product NPS — What to Do With Each Score

Collecting NPS data without acting on it is worse than not collecting it at all — you've burned a customer's time and attention for nothing. Here's how teams that actually move the needle handle each segment:

Detractors (0-6): Respond within 24 hours. Set up real-time alerts that notify your CS team the moment a detractor submits. The goal isn't to change their score — it's to show them someone heard them. Teams that follow up with detractors within one business day recover 30-40% of at-risk accounts. Use CX automation to route detractor responses directly to the owning CSM or support rep.
Passives (7-8): Don't ignore them. Passives are the most dangerous segment because they feel "fine" — and "fine" means they'll leave the moment a competitor offers something slightly better. Ask a follow-up: "What's the one thing that would make you a 9 or 10?" You'll get surprisingly specific answers that reveal your next product improvement opportunity. Track passives through targeted passive engagement workflows.
Promoters (9-10): Activate them. Promoters are your unpaid marketing channel. Route them toward review requests, referral programs, or case study participation. The window is narrow — ask within 48 hours of the NPS response while their enthusiasm is fresh. Connect with HubSpot to tag promoters in your CRM and trigger referral sequences automatically.

Pro tip: Don't just close the loop with individual respondents — close the organizational feedback loop too. Feed NPS themes into product planning. If 30% of detractors mention the same pain point, that's not a support issue — that's a product roadmap decision.

Automating Your Product NPS Survey — When and How to Trigger

The biggest mistake with product NPS surveys: sending them on a calendar schedule ("quarterly NPS blast") instead of triggering them around meaningful product moments. Calendar-based NPS gives you an average sentiment number that's too blurry to act on.

Trigger after meaningful usage milestones. Don't survey a user who signed up yesterday. Trigger the product NPS survey template after they've completed their first real workflow — created their first report, sent their first campaign, closed their first ticket. That's when they have enough experience to give you a meaningful score.
Use cooldown periods. Set survey throttling so no user sees the NPS survey more than once per quarter. Over-surveying creates survey fatigue and tanks your response rates. For SaaS NPS programs, once every 90 days per user is the sweet spot.
Deploy in-app for transactional signals, email for relationship signals. In-app NPS via website surveys or mobile SDK captures real-time product sentiment. Email NPS captures relationship sentiment. Run both, but label them differently in your reports so you're not mixing signals. Read the SaaS NPS measurement guide for deployment patterns by product type.
Automate segment-based follow-ups. Connect your product NPS survey template to Intercom or your helpdesk and set automated workflows: detractor → support ticket, passive → follow-up email, promoter → review request. This turns a survey into a feedback loop that runs without manual intervention.

Why Product NPS Matters — the Business Case

Product NPS isn't a vanity metric if you use it correctly. Here's what the data shows:

Retention predictor. A sustained NPS drop of 10+ points correlates with a 15-25% increase in churn over the following two quarters. By the time churn shows up in your revenue numbers, you're already behind. Product NPS gives you the early warning signal that usage data alone misses — because usage can stay stable while satisfaction erodes underneath.
Roadmap validator. Teams that tie product roadmap decisions to NPS follow-up data ship features that move the score. Teams that build based on competitor feature lists or internal intuition don't. The follow-up question in this product NPS survey template gives you the qualitative data to prioritize what actually matters to users.
Revenue lever. Promoters spend 2-3x more than detractors and have 5-7x higher lifetime value. Read more on NPS impact on revenue. Moving 10 passives to promoters is worth more than acquiring 20 new customers — and it's cheaper.

Use sentiment analysis on your NPS follow-up data to spot emerging themes before they become full-blown retention problems. Track theme frequency over time with survey reports — when a theme that affected 5% of responses last quarter jumps to 15%, that's your signal to act.